Blackenergy

Overview

BlackEnergy is an advanced, modular persistent threat (APT) framework originally authored in 2007 by Ukrainian hacker Dmytro Oleksiuk (alias 'Cr4sh') as an underground HTTP-based distributed denial-of-service (DDoS) botnet. Between 2010 and 2014, the codebase was heavily overhauled and co-opted by Russian state-sponsored threat actors—specifically the Russian General Staff Main Intelligence Directorate (GRU) Unit 74455 and Unit 26165, collectively tracked worldwide as Sandworm Team (TeleBots, Voodoo Bear). Under Sandworm development, BlackEnergy 2 and BlackEnergy 3 evolved into a multi-tiered cyber espionage and industrial sabotaging platform. The framework utilized rootkit drivers, modular DLL payloads, and specialized industrial control system (ICS/SCADA) plugins targeting serial-to-ethernet converters and Human-Machine Interface (HMI) workstations. On December 23, 2015, Sandworm deployed BlackEnergy 3 alongside the destructive KillDisk wiper component against Ukraine's electricity distribution grid (Kyivoblenergo), severing power to approximately 230,000 citizens in the world's first publicly acknowledged electrical blackout triggered by a cyber weapon. BlackEnergy was subsequently highlighted in the October 2020 US Department of Justice indictment charging six GRU Unit 74455 officers with global cyber intrusions.

Known aliases

Threat reports may refer to this family under multiple names:

• BlackEnergy
• BlackEnergy 2
• BlackEnergy 3
• Sandworm Toolkit
• Win32/BlackEnergy
• Backdoor.BlackEnergy

Threat Actor Attribution

Attribution is probabilistic, not a science. Each link below states its confidence level and the evidence behind it.

• Russian GRU Unit 74455 (Sandworm Team / TeleBots) / Dmytro Oleksiuk (Cr4sh) High confidence
  Basis: US Department of Justice October 2020 federal indictment of six GRU military officers for Sandworm cyberattacks, corroborated by US CISA, FBI, and Ukrainian CERT (CERT-UA) alerts identifying BlackEnergy in the 2015 Ukrainian power grid blackout. [source]

Family Pedigree & Lineage

Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:

Known Derivatives & Downstream Variants: Blackenergy V1 (Ddos) · Blackenergy V2 (Rootkit) · Blackenergy V3 (Ics/Scada) · Killdisk Wiper Module

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:

Tactical Mitigations

Based on the techniques used by this family, consider the following defensive strategies:

• T1059.003: Restrict execution of Windows Command Shell (cmd.exe) and block unauthorized batch scripts.
• T1071.001: Implement web filtering and SSL/TLS inspection to detect malicious command and control (C2) traffic hiding in HTTP/HTTPS.

MITRE D3FEND™ Defensive Countermeasures

Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):

Exploited Vulnerabilities (CVEs)

This malware family is documented weaponizing the following common vulnerabilities and exposures:

• CVE-2014-4114 — In-depth exploitation analysis and catalog intelligence (NIST NVD ↗).

Command & Control (C2) and Network Profile

How this family talks to its operators. C2 traffic can often identify a family even when its code and configuration are hard to analyse. Ports and patterns are historical and change between campaigns, so use them as hunting leads rather than block-only rules.

Indicators of Compromise

Public indicators drawn from CISA advisories and vendor reporting. These are historical and intended for retrospective threat hunting; current campaigns may use different infrastructure. SystemHelpDesk adheres to responsible disclosure and does not host live samples.

File hashes (SHA-256, sample)

Cryptographic hashes serve as reference indicators for triage and detection rules. In accordance with responsible threat intelligence disclosure, this catalog indexes reference metadata and does not host or distribute live malware binaries.

• 0f62d1c9ad9a64797a731efc1b4cfb0cc5a1b5d12de1d668749a46995642456e
• 294ac5e533c37560d2b8feeb492f58cfcb6c3c6efec24bb93b22cfd8ccb05612

Delivery vectors

• Spear-phishing emails containing malicious Microsoft PowerPoint (.pps/.ppt) documents weaponized with CVE-2014-4114
• Phishing emails disguised as official Ukrainian energy authority communications delivering weaponized macro-enabled Excel sheets

Persistence mechanisms

• Kernel-mode rootkit drivers installed in %SYSTEM32%\drivers
• Scheduled Tasks executing rundll32.exe with encrypted configuration files in %APPDATA%

Tiered Detection Rules (Cisco CAIRN Model)

Modern threat detection requires multi-layered rule engineering. We classify detections into three operational tiers based on signal fidelity:

rule MALWARE_WIN_BLACKENERGY_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Blackenergy"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "blackenergy" ascii wide nocase
        $s2 = "blackenergy" ascii wide nocase
        $s3 = "blackenergy 2" ascii wide nocase
        $s4 = "blackenergy 3" ascii wide nocase
        $s5 = "sandworm toolkit" ascii wide nocase
        $s6 = "win32/blackenergy" ascii wide nocase
        $s7 = "backdoor.blackenergy" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Blackenergy (Advanced Threat) Execution & Triage
id: 6226fa75-1e9c-540d-8db9-19039cd43bbe
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Blackenergy malware family. Detects proxy execution, reflective DLL loading,
  and remote command injection associated with modular enterprise backdoors.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/blackenergy
- https://malware-families-catalog.systemhelpdesk.com/defensive/backdoor-rat-protection
- https://malware-families-catalog.systemhelpdesk.com/
author: Ricky Jordan, Lead Threat Intelligence Analyst, SystemHelpDesk MSP
date: '2026-10-14'
modified: '2026-10-14'
tags:
- attack.advanced-threat
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1055
- attack.t1059_003
- attack.t1562_001
- attack.t1485
- attack.t1071_001
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \powershell.exe
    - \cmd.exe
    - \rundll32.exe
    - \regsvr32.exe
    CommandLine|contains:
    - DownloadString
    - IEX(
    - '/s /n /u /i:'
    - sc create
    - start-process
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: high

rule MALWARE_WIN_BLACKENERGY_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Blackenergy tradecraft"
        tier = "T3 - Attribution Fingerprint"
        confidence = "High (Confirmed Family Signature)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        // Core family identifier & heuristic payload signatures
        $attrib_str = "blackenergy" ascii wide nocase
        $pe_magic = "MZ" ascii
        $net_marker = "http" ascii nocase
    condition:
        uint16(0) == 0x5a4d and ($attrib_str and $net_marker) and filesize < 15MB
}

Containment & Response Steps

Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.

1. Enforce forensic network isolation on all suspected endpoints while maintaining an out-of-band telemetry conduit to capture live Blackenergy adversary activity.
2. Perform full memory dumps across identified staging nodes to extract memory-only implants, kernel rootkit hooks, and decrypted Blackenergy C2 infrastructure IP/domain lists.
3. Review Active Directory domain controller authentication logs for anomalous Kerberos ticket requests (Pass-the-Ticket, Golden Ticket) and unauthorized DCSync operations associated with Blackenergy.
4. Block all confirmed C2 domains, dynamic DNS endpoints, and proxy IP addresses across perimeter firewalls, proxies, and DNS security gateways.
5. Conduct an enterprise-wide sweep across surrounding subnets for secondary webshells, WMI event subscriptions, or remote execution tooling left behind by Blackenergy operators.

What to Avoid

Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.

1. Do not assume the incident is resolved simply because an antivirus tool removed the initial Blackenergy dropper; always verify that secondary payloads and persistence hooks have been eradicated.
2. Avoid logging in with Domain Admin or privileged credentials on a machine suspected of running Blackenergy until memory triage is complete.
3. Do not delay host isolation; automated lateral movement and credential dumping can occur within minutes of initial execution.

References & External Analysis

• US DOJ Indictment of Six Russian GRU Officers
• CISA Advisory - Cyber-Attack Against Ukrainian Critical Infrastructure
• MITRE ATT&CK - BlackEnergy (S0089)
• Search "blackenergy" on VirusTotal (External Analysis)
• Search "blackenergy" on Any.Run (Sandbox Sandbox)
• Search "blackenergy" on MalwareBazaar (Malware Samples)

Frequently Asked Questions

Related Threats (Category: Advanced Threat)

Explore other documented threats in the same operational category:

• Cloudscout
• Rontokbr
• Xyntservice
• Hostschanger
• Spectorpro
• Iwin
• Netcat
• Qqfarmassist

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/blackenergy.json

Ecosystem & Interactive Environments

This profile is part of the Malware Families Catalog, a public dataset of 2,899 malware families. The catalog is also published across our ecosystem: Hugging Face, Kaggle, Zenodo, Replit, StackBlitz, CodeSandbox, and CodePen.